Arcserve

Arcserve® Unified Data Protection Version 5.0 Update 1 Release Notes

1.0 Welcome

2.0 Enhancements

3.0 Issues Fixed

4.0 Known Issues

5.0 Limitations

6.0 Installation
6.1 Prerequisite Tasks
6.2 Installation Instructions

7.0 Contact Arcserve Support

1.0 Welcome

Welcome to the Arcserve UDP Version 5.0 Update 1 Release Notes. This Release Notes contains important information about this update.

2.0 Enhancements

The following enhancements have been added to Arcserve UDP for this update:

Upgraded Tomcat to version 7.0.54

Test Fixes installed. For more information, see Issues Fixed in the Release Notes.

3.0 Issues Fixed

This update fixes the following issues, which could have occurred:

A virtual machine (VM) with an MS Exchange or MS SQL application installed, may inadvertently use a standard socket type of license for a hypervisor instead of a virtual machine type license. This could occur if the VM is protected by a Arcserve UDP Agent which is installed inside the VM and you have used the "Specify Hypervisor" function to force the VM to use a Hypervisor level license. Since the VM has an application which requires a different license, Arcserve UDP will then use a virtual machine type license and fail to release the standard socket type license. If this occurs, you need to manually un-assign the standard socket type license from this hypervisor so that it can be used someplace else.

When Arcserve UDP Agent (Windows) is installed inside the VM and you specify a hypervisor, even the OS of Arcserve UDP Agent (Windows) is Workstation, SBS and Essential, the Agent could not use Arcserve UDP Version 5.0 Socket Essentials License.

This problem happens when a Hyper-V server is not shut down properly (for example, lost power or OS crash), and at the same time, after the Hyper-V server resumes, the first backup job fails or is canceled/killed. In this case, there may be data corruption in the backed up data until the next full backup.

Set the Concurrent Active Nodes to N; there might be N File system catalog jobs running for the Windows Agent, and another N File system catalog jobs running for Agentless nodes.

An RPS server can be deleted even if a plan is using it.

For a powered-off VM that is protected by a host-based backup task, the VM node is not wrapped with VM() in the Log view. The VM name is shown as NodeName value, so that all filters can work as planned.

If the following two conditions exist, the hash memory for the data store is displayed incorrectly when modifying the data store:
- The memory of the RPS server is less than or equal to 4 GB.
- You do not select the maximum value for the hash memory when creating a data store.

This problem occurs when a merge is scheduled to run within a time window. After the time window is reached, you see a link Run a merge job manually now on the Summary panel of the Arcserve UDP Agent (Windows) home page. When the link is clicked, the merge does not get launched. The manual merge does not ignore the merge time window.

The consequent merge job will fail if the last merge job failed to delete the session data folder.

When a plan is paused, select multiple nodes managed by this plan, and submit a backup job. The following error message is not correct: "Failed to delete Backup job is paused. Check if this configuration file is currently open. If open, please close it and then try again to delete. If not open, please try again at a later time".

A new makeup job gets triggered when you cancel the makeup job of replication. In general, canceling the job should not trigger a makeup job and therefore "the retry count configured for replication task" should not be applicable for canceled jobs.

The consequent host-based backup incremental backup job will fail if the last backup job failed due to a file in the occupied status.

When you add nodes from a Hyper-V or vCenter/ESX, the status bar becomes disabled, and the pagination and refresh buttons do not work.

When remote scan fails due to the firewall, the web service empties the password field and connects the Agent service. As a result, the user credential validation fails if the Agent firewall is not turned off.

Change deployment result message from "Please consult to your network administrator" to "Please consult your network administrator".

BMR collects all logs files during bare metal recovery. If the source and destination folder are the same, the copied log files are corrupted.

In Log view, the NodeName filter and the GeneratedFrom filter do not work if the input node name contains the character '_' .

Canceling a replication job at some particular point will cause the replication job to crash.

If the backup session format is standard VHD format, when you merge one full session and one incremental session, the merge job fails.

The following message in the activity log is incorrect: "Stop the target datastore when a jumpstart job is running."

After you specify a hypervisor for the Linux node, the node type for the Hypervisor is Linux, instead of Hypervisor in License Management.

The Total column of the Managed Capacity license will display <Count>, instead of <Count>TB in License Management.

When you enter a non-Managed Capacity license where the count number is greater than 900,000,000, the License Management window displays the license count as the actual count, instead of Unlimited.

When the VM has many disks, and the full path of each disk file is very long, then the host-based backup of this VM may fail.

When protecting a Hyper-V virtual machine, if the virtual machine has a disk with Fixed Size type and this disk has a child disk, after this virtual machine is recovered, the disk type of this disk is incorrectly changed to Dynamic Expanding.

When there is not enough free space on the VM recovery destination, the recovery job failure message should give the appropriate details.

When you log in to Arcserve UDP, and select "Do not show this message again" from the Getting Started dialog, the dialog should not display after you log in again.

A host-based backup job fails with a license failure when the Hypervisor is VMware vSphere Essentials Kit or VMware vSphere Essentials Kit Plus, even if there is a Arcserve UDP Version 5.0 socket license key available.

When you add a Linux node using the IP address and then specify a hypervisor for this node, the node name is changed to hostname, and cannot submit a backup job for this node.

For all issues fixed in this release, see the Arcserve UDP Version 5.0 Release Notes.

4.0 Known Issues

The following issues could exist in this update:

The Arcserve UDP Console does not show the latest version information of the locally installed agent immediately after installation of Update 1, when the agent and console are installed on the same machine.
Symptom

When the agent is installed on the same machine, and after installing Update 1, the Arcserve UDP Agent (Windows) version information in the node view may not be updated immediately.

Solution
1. Force the refresh by using the Update node action on the node.
2. Wait about 15 minutes for the information to be automatically updated.

Merge jobs fail when backing up a VM that has an un-initialized disk and is restored from a host-based backup.

The installation of Update 1 for the Arcserve UDP Console fails when it is performing a remote deployment for another RPS server.
Symptom

When the Arcserve UDP Console is performing a remote deployment of RPS, and at the same time, on the Arcserve UDP Console machine, you check for updates and install the update, you will get the following error in the activity log: "Failed to install update for Console (Error code: -520026872).

Solution

After the deployment of RPS finishes, continue to install the update on the Arcserve UDP Console machine.

When the Arcserve UDP Console is installed on one machine, and RPS and the host-based backup proxy are installed on another machine, if you install Arcserve UDP Version 5.0 Update 1 on the Console machine and then try to deploy a plan, the plan deployment fails.
Solution

Upgrade RPS first before modifying the plan.

After a VM restore, the file size of the fixed VHDX disk file is smaller than the disk size.
For example, perform the following steps:

1. Back up a VM with a fixed size VHDX disk, with a size of 10GB.

2. Restore that VM.

3. In Hyper-V Manager, if checking the disk type, you can see that the VHDX disk is kept as a fixed size disk.

4. However, if checking the file size of that disk file in the OS, its size is smaller than the disk size (10GB).

Note: This only happens with a fixed VHDX in Hyper-V 2012. There is no data loss within the virtual disk and the VHDX disk works fine, however it behaves like a dynamic VHDX disk.

After performing a restore job for a host-based VM backup Hyper-V virtual machine (VM), the status of the disks, except the boot disks on the recovered virtual machine is Offline.
Symptom

The behavior of the operating system creates the offline state by default.

The SAN policy was introduced in Windows Server 2008 to protect shared disks that are accessed by multiple servers. The default SAN policy from the source VM is “Offline Shared” for all SAN disks except the boot disk. Setting the policy to Offline enables the SAN disks to be offline during startup. After recovery, a new disk for the VM is created. The disk file from the VM appears to be a SAN disk where the operating system identifies it as being offline. When the offline disk is set to be back online, the disk remains online even after rebooting the system.

Solution

As a workaround, specify the DISKPART.exe command: SAN POLICY=OnlineAll setting for the source VM before backup. Because the disks can be shared among other servers, data corruption can occur. You must use the correct SAN policy to protect the data.

DISKPART.EXE command line

Query SAN policy:

DISKPART > san

SAN Policy: Offline Shared

Change SAN policy:

DISKPART > san policy=OnlineAll

DISKPART successfully changes the SAN policy for the current operating system.

For all known issues in this release, see the Arcserve UDP Version 5.0 Release Notes.

5.0 Limitations

In an Exchange Database Availability Group (DAG) environment, Arcserve Central Host-Based VM Backup can only truncate logs for the protected Exchange nodes. The following alternatives will result in log truncation on all DAG nodes:
- Back up all nodes in a DAG.
- Install the Agent inside the virtual machine on the active nodes by applying the procedure from the following KB article:http://www.arcserve-knowledgebase.com/index.php?View=entry&EntryID=3154.
- Use Arcserve Backup Exchange Agent.

For all limitations in this release, see the Arcserve UDP Version 5.0 Release Notes.

6.0 Installation

The following sections provide information about installation prerequisites and installation instructions.

6.1 Prerequisite Tasks

Consider the following prerequisite tasks before installing this update:

Before you install this update, verify that Arcserve UDP Version 5.0 is installed.

6.2 Installation Instructions

When installing the Arcserve UDP update or the Arcserve UDP Agent (Windows) update, it is important to maintain optimal performance between the Console, the Recovery Point Server (RPS), and the Agents. As a result, when the update is installed in an environment that contains both a Console and an Agent, you must always install the update on the Console first, and then on the RPS, and finally on the Agent. (For the Agent that is installed on the Console or the RPS, the update will be automatically installed on that Agent at the same time).

Important! When updating to Arcserve UDP Version 5.0 Update 1, a system reboot may be required.

You can use two methods to install the update; by using the update utility or manually:

Installing the Update Using the Update Utility

To install the update using the update utility from the Home Page, follow these steps:

Open and log in to Arcserve UDP (Full installation) or Arcserve UDP Agent (Windows) (Agent only installation).

Update the Arcserve UDP Console (Full installation) or Arcserve UDP Agent (Windows) (Agent only installation):
1. From the top right corner of the Home Page, click Help, and then click Check for Updates.
2. Follow the on-screen instructions to install and apply the update.
Note: For the Full Installation, this step also automatically downloads the necessary packages for remote deployment to the RPS and the Agent. For the Agent only installation, this completes the update process.

Update the Recovery Point Server:
1. From the left pane, click Recovery Point Servers.
2. Select the RPS, click Actions and then click Install/Upgrade Recovery Point Server to upgrade each RPS.
3. Follow the on-screen instructions to install and apply the update.

Update the Agent (Full installation) using one of the following methods:
- Redeploy the plan to automatically update the Agent nodes.
- Use the Node view to update the Agent nodes.
  1. Click Node view and then click All Nodes.
  2. Select the nodes, click Actions, and then click Install/Upgrade Agent to update each agent.
  3. Follow the on-screen instructions to install and apply the update.

Note: For more information about updating Arcserve UDP, see the Solutions Guide. For more information about updating Arcserve UDP Agent (Windows), see the Agent for Windows User Guide.

Installing the Update Manually

To download and install the update manually, use the following links to the installation files:

Arcserve Unified Data Protection:
http://downloads.arcserve.com/UDPUpdates/FullUpdates/r5.0/arcserve_Unified_Data_Protection_Update_1.exe

Arcserve Unified Data Protection Agent:
http://downloads.arcserve.com/UDPUpdates/EngineUpdates/r5.0/arcserve_Unified_Data_Protection_Agent_Update_1.exe

7.0 Contact Arcserve Support

The Arcserve Support team offers a rich set of resources for resolving your technical issues and provides easy access to important product information.

www.arcserve.com/support

With Arcserve Support:

You can get in direct touch with the same library of information that is shared internally by our Arcserve Support experts. This site provides you with access to our knowledge-base (KB) documents. From here you easily search for and find the product-related KB articles which contain field-tested solutions for many top issues and common problems.

You can use our Live Chat link to instantly launch a real-time conversation between you and the Arcserve Support team. With Live Chat, you can get immediate answers to your concerns and questions, while still maintaining access to the product.

You can participate in the Arcserve Global User Community to ask and answer questions, share tips and tricks, discuss best practices and participate in conversations with your peers.

You can open a support ticket. By opening a support ticket online, you can expect a callback from one of our experts in the product area you are inquiring about.

You can access other helpful resources appropriate for your Arcserve product.